-
Notifications
You must be signed in to change notification settings - Fork 208
Upgrade to otel sdk v2 #1789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to otel sdk v2 #1789
Conversation
…ble is no longer exported in version 2.0.0
…feat/nodejs/upgrade-otel-sdk
…recated addSpanProcessor method, remove support for configureTracerProvider global method
… configureTracer global func
Hi @wpessers, any plans to merge it soon? |
@rndD I will be doing some final testing tonight hopefully. Things should move quickly from there. But be aware that I can't guarantee when the next version for the layer will be released, this might take some time still after the PR has been merged. |
@wpessers, thanks for the detailed answer. Can you tell me the current cycle or strategy for layer releases? |
I will have to refer you to @serkan-ozal @tylerbenson @pragmaticivan for this question. As far as I'm aware there's no strict release cycle. It's just that when we are ready to release a certain change for a language specific layer, we want to make sure to also include "low-hanging fruit" (like dependency upgrades) for the different language-specific layers. And if there happens to be some change in another layer that we want to release, this may hold back the entire release a little bit. So that we don't have to do multiple releases after one another in a short period of time. |
…entelemetry-lambda into feat/nodejs/upgrade-otel-sdk
Still work in progress. Most of it should be covered by this PR, butstill doing some smoke-testing on my own lambdas